Netware Super Library

home *** CD-ROM | disk | FTP | other *** search

/ Netware Super Library / Netware Super Library.iso / mhs_mail / xgate3 / xgate.cfg < prev next >

Wrap

Text File | 1993-12-15 | 18.6 KB | 446 lines

;============================================================================== ; XGATE Configuraton File ;------------------------------------------------------------------------------ ; The C-Configuration option on XGATE's main menu can be used to double-check ; proper detection of configuration fields. ; ; The format of the configuration file is very 'loose'. Any amount of white ; space (tabs or spaces) can be used to separate a field name from its value. ; A semi-colon begins a comment. Any leading white space before a comment is ; also discarded. ;------------------------------------------------------------------------------ ; MHS-Related Fields ;------------------------------------------------------------------------------ mhs_path sys: ;Root path to MHS directory structure. mhs_gateway_name smtp ;Our gateway name under MHS. mhs_default_host ;If mail is received from SMTP without ; a MHS hub name specified, the name ; of the workgroup entered in MHS is ; used automatically unless overridden ; here. (Not normally needed.) mhs_administrator frailey ;Send error messages to a different ; name than the MHS administrator. mhs_admin_errors Y ;MHS administrator gets error messages. include_header N ;Whether to include the entire SMTP ; header in the MHS message. If set ; to "Y" or "B", the received SMTP ; header is copied in at the start ; of the MHS body text. If set to ; "H", the complete SMTP header is ; encapsulated in the MHS header. ; The "H" option is useful if your ; E-Mail app provides a way to view ; fields in the MHS message header. include_smtp_fields RFTC ;Include specific SMTP header fields ; in MHS msg body; R=Reply-To:, ; F=From:, T=To:, C=Cc:. ; Note: Only one of the 3 previous ; options should probably be enabled ; at one time. use_mhs_total_fields N ;Build MHS "Total-To:" & "Total-Cc-To:" ; fields from SMTP messages. use_smtp_repto_as_from N ;If your E-mail application doesn't ; recognize a SMF-70+ Reply-to field ; in the SMF header (which Xgate ; builds if the SMTP msg contains ; one), you will probably want to ; turn this option on so that the ; MHS From: field will contain the ; proper address to reply to. append_ascii_attach 50 ;Controls whether attached MHS files ; that contain only ASCII characters ; are appended to the body text of ; outgoing SMTP messages. The value ; specified is the maximum file size ; (in K) of attachments that will be ; considered. Attached files having ; a bigger file size or that contain ; non-printable characters are skipped. ; A value of 0 disables this option. ; If a file attachment isn't processed ; by this option, it will be uuencoded ; if uuencoding is enabled. conv_body_to_attach 0 ;If the body text of an inbound SMTP ; message is bigger than this number ; (in K), the body text is rolled off ; to an attachment. Some PC-based ; MHS E-Mail applications (i.e. Beyond ; Mail) can't handle a message with ; body text bigger than a certain size ; (32k in the case of Beyond Mail). ; A value of 0 disables this option. ignore_lwsp_after_fold N ;Controls whether linear white space ; characters after an MHS folded header ; line are considered significant. ; This option is rather technical and ; should normally be set to "N". It is ; needed in some circumstances when an ; MHS application does not properly ; conform to the MHS rules for line ; folding of header fields (WPO is one ; that doesn't and needs this option ; set to "Y"). Refer to XGATE's ; documentation for more information. static_reply_address N ;Controls the MHS reply address mode. ; With this option off, the MHS reply ; address for inbound SMTP mail is ; built using a combination of the ; first 8 chars of the SMTP username ; @ XGATE's gateway name (plus the ; SMTP address in the MHS extended ; address), which is the conventional ; way to address mail to a gateway. ; MHS however, will also route mail ; fine to XGATE if the gateway name ; preceeds the MHS workgroup name. ; (i.e. "SMTP@ACME {smtp_address}") ; where SMTP is the gateway name and ; ACME is the MHS workgroup name. ; If you'd rather use the latter ; syntax, enable this option. native_smf71 N ;Under SMF-71 (MHS 2.0) address masks ; can be defined which route messages ; that qualify to a particular host or ; gateway, removing the need to use ; "user@host{internet_addr}" syntax. ; Instead, mail can be sent using ; native SMTP syntax, provided all ; possible destination addresses have ; a mask defined (i.e. **.com, **.gov, ; **.edu, etc...). When XGATE is ; defined under Global MHS as a gate- ; that understands these address ; formats - enabling this option ("Y") ; tells XGATE not to look for the ; "{}" portion in the address, but ; rather to treat the entire address ; to the right of "@" as the SMTP ; recipient's address. It also tells ; XGATE not to build the return SMTP ; address using that syntax. This ; option will only work if NETDIR.TAB ; indicates SMF-71 or greater. ;------------------------------------------------------------------------------ ; SMTP-Related Fields ;------------------------------------------------------------------------------ smtp_gateway_name mhs.com ;Our TCP/IP host name. smtp_default_host darius.com ;The default SMTP host to address a ; message to if an MHS message doesn't ; specify the destination SMTP host. smtp_timezone pst ;Timezone stamped on outbound SMTP ; dates if the MHS message didn't ; use a UTC desigination (i.e.+0800). ; This can be expressed as either ; a valid 3 char North America time ; zone, or a UTC designation such ; as -0800. conv_time_to_local N ;Determines whether XGATE converts ; the time of SMTP messages received ; to local time. In order for this ; to work right, the smtp_timezone ; must be set correctly. smtp_exclude_mhs_hub N ;Excludes the MHS hub name when ; building an SMTP return address. smtp_include_mhs_app N ;Includes the sending MHS application ; name (if its given) in the return ; address of the MHS sender. This ; option is not normally needed for ; E-Mail only type messages since ; MHS automatically routes inbound ; mail to the user's preferred app. ; In some cases though, you may need ; to enable it if dealing with a ; large number of users and multiple ; MHS applications. smtp_receipts N ;Generate an MHS return receipt for all ; inbound SMTP mail. use_mhs_ret_rcpt Y ;Ask for an SMTP receipt if the MHS ; message had it on. (Embedding a /r ; in the outbound smtp address of the ; mhs message's gateway parameters is ; recognized regardless of this ; setting.) name_mapping_mode 0 ;SMTP name translation mode. If set ; to 0, reply addresses are built ; according to SMF-71 conventions ; with a "%" separating the user name ; from the workgroup. If set to 1, ; a period is used. This only affects ; the format of reply addresses. When ; receiving an SMTP message, XGATE will ; work properly if either a "%" or a ; "." separates the workgroup from the ; user name. smtp_user_suffix ;Optional text appended to an MHS ; user's name, before the gateway ; host name, in the return address ; (not normally used). ;------------------------------------------------------------------------------ ; Uuencode-Related Fields ;------------------------------------------------------------------------------ uuencode Y ;Enable automatic uuencoding of ; outbound MHS attachments, and ; decode scanning of each inbound ; SMTP message. ;Decode headers: ; These are fields automatically ; embedded in the SMTP header when ; it contains a uuencoded file. The ; idea is to automatically trip the ; recipients mailer into decoding ; the enclosed file. Embedding %fn ; will expand into the name of the ; uuencoded file. Decode headers ; can be defined more than once - ; but they all go in a message with ; uuencoded files. decode_header Next-Attachment: %fn ; For Next Computers decode_header Content-Type: x-uuencode-apple-single ; For Apple Computers scrap_mhs_attach *packed* ;Scrap (don't uuencode) MHS attachments scrap_mhs_attach *beyond* ; that have this filename. This field ; can be defined more than once. ;------------------------------------------------------------------------------ ; Miscellaneous Fields ;------------------------------------------------------------------------------ scan_frequency 10 ;Scan for new mail every n seconds. black_and_white N ;Use black and white video mode. mute N ;Whether speaker beeps on errors. screen_save 0 ;Blank screen after this many minutes. ; A value of 0 disables screen saver. inbound_log ;Path and filename of inbound log file outbound_log ;Path and filename of outbound log file error_log ;Path and filename of error log file mhs_scrollback_lines 50 ;MHS Activity scroll back lines. If ; expanded memory is present, this ; value is ignored and a 64k buffer ; (or as much as is available) is ; allocated. smtp_scrollback_lines 100 ;SMTP Monitor scroll back lines. If ; expanded memory is present, this ; value is ignored and a 64k buffer ; (or as much as is available) is ; allocated. ;------------------------------------------------------------------------------ ; SMTP Server Module Variables ;------------------------------------------------------------------------------ watch_dog 30 ;Reboot the computer after this many ; seconds if the process time slicer ; is no longer running. This only ; works if hardware interrupts are ; still functioning. Using zero ; disables the watchdog. Otherwise, ; a value below 10 results in 10. max_xmit_processes 20 ;Maximum Concurrent Transmit Processes ; The Mach 2 TCP/IP stack supports ; 100 concurrent sessions, but this ; is not normally attainable unless ; the number of file handles is also ; raised to 100 (the NetWare default ; is 40). Limiting the maximum number ; of concurrent transmit sessions ; ensures at least x number of receive ; processes are available. relay_mode 0 ;Relay Mode: ; 0 = Attempt direct delivery first ; using domain name servers. ; If resolve error or if host ; unreachable, pass message to ; to the relay host. ; 1 = Attempt passing message to ; relay host first, if that fails ; attempt direct delivery if one ; or more name servers are given. relay_host 129.194.30.5 ;Relay Host: ; If specified, it must be a fully ; qualified NUMERIC IP address. ; If not specified, a name server must ; be given below so direct delivery ; can be attempted. connect_timeout 20 ;Time to wait in seconds before ; considering an outbound connection ; timed out. reschedule_minutes 5 ;The number of minutes to wait before ; reattempting an outbound message ; which fails to connect. undeliverable_hours 72 ;Return mail to sender after this many ; hours if unable to move the message. ; If a relay host is defined, this ; timeout is normally not encountered. resolve_minutes 15 ;Return mail to sender after this many ; minutes if unable to resolve the ; destination host using name servers. ; If a relay host is defined, this ; timeout is normally not encountered. name_server 129.194.30.5 ;1st name server (MyLocalUnixBox) name_server 192.112.36.5 ;2nd name server (NS.NIC.DDN.MIL) name_server 128.9.0.107 ;3rd name server (A.ISI.EDU) ; Domain Name Servers must be fully ; qualified numeric IP addresses. ; Up to 10 name servers can be defined ; by repeating these variables. An ; address can be used more than once ; in sequence to extend the response ; time allowed for a particular name ; server. domain_timeout 7 ;Domain Name Server Timeout. ; Time to wait in seconds on each ; name server before querying the ; next name server. If multiple ; name servers are given, a late ; response from a query to a previous ; server will still be recognized. ;------------------------------------------------------------------------------ ; TCP/IP Protocol Binding ;------------------------------------------------------------------------------ ; IP addresses are bound logically inside XGATE to either an ODI driver, ; or a Clarkson Packet Driver. More than one BIND statement can be used ; to support multiple IP addresses and/or interfaces, but such usage is ; rare with XGATE. ; ; The format of the BIND statement is: ; ; BIND <ip_address>, <netmask> [,<interface>] [,<bcast>] ; ; <ip_address> is the local IP address being bound to an interface board ; (which will be XGATE's local IP address). ; ; <netmask> is the portion of the IP address that represents the network ; part (which is what XGATE uses to determine when a packet is destined ; to a remote network, and has to be routed). ; ; Both the <ip_address> and <netmask> are expressed as fully qualified ; IP addresses in dotted notation. ; ; <interface> is an optional parameter that explicitly tells XGATE what ; network interface to bind the <ip_address> to. In most cases this can ; be left out or set to zero and XGATE will automatically bind correctly to ; the next available interface driver that supports a TCP/IP frame type. ; Specifying an interface number is needed if more than one network card ; is present, or more than one frame type is present that supports TCP/IP. ; If the interface number is not given (or is zero) and XGATE does a default ; search for a compatible interface, an ODI driver is recognized before a ; Packet Driver, should both happen to be present. ; ; When specifying an interface number, the value can be expressed in either ; decimal or hex (hex values are given in C format by prefixing the number ; with a "0x"). ; ; If the interface number is a value between 1 and 16 (decimal), it is ; considered to be a reference to a logical MLID "board ID" number that ; was bound to a suitable frame type in NET.CFG (usually ETHERNET_II). ; (An MLID is a card-specific ODI driver.) ; ; If the interface number is a value between 17 and 255 (decimal), it is ; considered to be a reference to a Packet Driver configured to use that ; number as its software interrupt. Packet Driver interrupts are normally ; expressed in hexadecimal, so be sure to give the interface number prefixed ; with a "0x" if so appropriate. ; ; <bcast> is an optional parameter that overrides the normal use of 1's ; for broadcast bits in the host portion of an IP Address. If <bcast> ; is given, it can only be a value of 0 or 1. ;------------------------------------------------------------------------------ bind 130.23.4.7, 255.255.255.0, 0x00 ;------------------------------------------------------------------------------ ; TCP/IP Routing ;------------------------------------------------------------------------------ ; Route commands are used to initially seed the routing table with static ; routes, or to enable RIP, or a combination of both. When RIP is enabled, ; a broadcast query for RIP information is sent on all interfaces immediately ; upon startup. ; ; Normally the use of RIP is overkill (unless XGATE has more than one network ; interface), because all non-local packets will probably end up just needing ; to go to a default router (gateway), and using one simple static route to ; that default router will work just fine. If you enable RIP, and don't also ; give XGATE a static default route to the default gateway - XGATE may not be ; able to talk to all networks if the default gateway doesn't advertise itself ; through RIP as a default route on that network. The routing table can be ; examined from under the SMTP Monitor's "<D>river, <T>ables" command. ; ; The format of the ROUTE statement is: ; ; ROUTE <network>, <next_hop_gateway> [,metric] ; ROUTE RIP ; ; The first form adds a static route. The second form enables RIP, which ; is off by default. Up to 10 static routes can be given by using multiple ; route statements. ; ; A <network> given as all zeros is the equivalent of a default ; route (i.e. everything not destined for the local network qualifies, ; and those packets are then send to the <next_hop_gateway>). ; ; When more than one IP address is bound, XGATE will automatically make ; the correct association of which interface to route through. ; ; If the <metric> isn't specified, it is assumed to be 1. The metric ; is used as a means to prioritize routes when more than one qualifies. ; A default route is always given a metric of 17 (which is higher than ; the valid metrics 1..15) because default routes are only supposed to ; be used if no other route qualifies. ;------------------------------------------------------------------------------ route 0.0.0.0, 130.23.4.1 ;Route all non-local packets to ; address 130.23.4.1. ;------------------------------------------------------------------------------ ; TCP/IP Forwarding ;------------------------------------------------------------------------------ ; The TCP/IP protocol stack built into XGATE also has the ability to forward ; (route) packets between multiple interfaces. If you have more than one ; interface card installed and want XGATE to route packets between them, ; this option can be enabled with IPFORWARD command. ;------------------------------------------------------------------------------ ipforward N ;Whether to forward (route) IP packets ; between multiple interfaces, if more ; than one interface is installed.